-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix WCT for bower: use Polymer version of sinon.js #3489
Conversation
Repository github.com/blittle/sinon.js was deleted And bower install fails Workaround for Polymer/tools#3488 While Polymer/tools#3489 isn't merged and released
Repository github.com/blittle/sinon.js was deleted And bower install fails Workaround for Polymer/tools#3488 While Polymer/tools#3489 isn't merged and released
Repository github.com/blittle/sinon.js was deleted And bower install fails Workaround for Polymer/tools#3488 While Polymer/tools#3489 isn't merged and released
Repository github.com/blittle/sinon.js was deleted And bower install fails Workaround for Polymer/tools#3488 While Polymer/tools#3489 isn't merged and released
The integration tests are timing out on Chrome 80. This has been happening elsewhere though, see lit/lit#1080 and lit/lit#1078 |
@justinfagnani thanks. BTW, am I right that in order to make a release for Bower, this PR should go into (now archived) original web-component-tester repository? At least $ bower search web-component-tester
Search results:
web-component-tester https://github.com/Polymer/web-component-tester.git |
@web-padawan I think you're right. cc @dfreedm @usergenic |
We've unarchived the old repo and will add this fix there and tag a new release for Bower. |
Thanks a lot 🙇 Feel free to close this PR in that case. |
Fixes #3488
This is a fix for the critical issue that affects our bower installations:
Ping @justinfagnani @usergenic.